chore(deps): update pnpm to v10.19.0 #90

renovate · 2025-03-06T18:57:07Z

This PR contains the following updates:

Package	Change	Age	Confidence
pnpm (source)	`10.5.2` -> `10.19.0`

Release Notes

pnpm/pnpm (pnpm)

`v10.19.0`

Compare Source

Minor Changes

You can now allow specific versions of dependencies to run postinstall scripts. onlyBuiltDependencies now accepts package names with lists of trusted versions. For example:
```
onlyBuiltDependencies:
  - [email protected] || 21.6.5
  - [email protected]
```
Related PR: #10104.
Added support for exact versions in minimumReleaseAgeExclude #9985.

You can now list one or more specific versions that pnpm should allow to install, even if those versions don’t satisfy the maturity requirement set by minimumReleaseAge. For example:
```
minimumReleaseAge: 1440
minimumReleaseAgeExclude:
  - [email protected]
  - [email protected] || 5.102.1
```

`v10.18.3`

Compare Source

Patch Changes

Fix a bug where pnpm would infinitely recurse when using verifyDepsBeforeInstall: install and pre/post install scripts that called other pnpm scripts #10060.
Fixed scoped registry keys (e.g., @scope:registry) being parsed as property paths in pnpm config get when --location=project is used #9362.
Remove pnpm-specific CLI options before passing to npm publish to prevent "Unknown cli config" warnings #9646.
Fixed EISDIR error when bin field points to a directory #9441.
Preserve version and hasBin for variations packages #10022.
Fixed pnpm config set --location=project incorrectly handling keys with slashes (auth tokens, registry settings) #9884.
When both pnpm-workspace.yaml and .npmrc exist, pnpm config set --location=project now writes to pnpm-workspace.yaml (matching read priority) #10072.
Prevent a table width error in pnpm outdated --long #10040.
Sync bin links after injected dependencies are updated by build scripts. This ensures that binaries created during build processes are properly linked and accessible to consuming projects #10057.

`v10.18.2`

Compare Source

Patch Changes

pnpm outdated --long should work #10040.
Replace ndjson with split2. Reduce the bundle size of pnpm CLI #10054.
pnpm dlx should request the full metadata of packages, when minimumReleaseAge is set #9963.
pnpm version switching should work when the pnpm home directory is in a symlinked directory #9715.
Fix EPIPE errors when piping output to other commands #10027.

`v10.18.1`

Compare Source

Patch Changes

Don't print a warning, when --lockfile-only is used #8320.
pnpm setup creates a command shim to the pnpm executable. This is needed to be able to run pnpm self-update on Windows #5700.
When using pnpm catalogs and running a normal pnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when using pnpm add --save-catalog as originally intended.

`v10.18.0`

Compare Source

Minor Changes

Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

Added configuration options for warning thresholds: fetchWarnTimeoutMs and fetchMinSpeedKiBps.
Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

Related PR: #10025.

Patch Changes

Retry filesystem operations on EAGAIN errors #9959.
Outdated command respects minimumReleaseAge configuration #10030.
Correctly apply the cleanupUnusedCatalogs configuration when removing dependent packages.
Don't fail with a meaningless error when scriptShell is set to false #8748.
pnpm dlx should not fail when minimumReleaseAge is set #10037.

`v10.17.1`

Compare Source

Patch Changes

When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #9974.
Fix state.json creation path when executing pnpm patch in a workspace project #9733.
When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #9987.

`v10.17.0`

Compare Source

Minor Changes

The minimumReleaseAgeExclude setting now supports patterns. For instance:
```
minimumReleaseAge: 1440
minimumReleaseAgeExclude:
  - "@&#8203;eslint/*"
```
Related PR: #9984.

Patch Changes

Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #9978.
When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #9979.

`v10.16.1`

Compare Source

Patch Changes

The full metadata cache should be stored not at the same location as the abbreviated metadata. This fixes a bug where pnpm was loading the abbreviated metadata from cache and couldn't find the "time" field as a result #9963.
Forcibly disable ANSI color codes when generating patch diff #9914.

`v10.16.0`

Compare Source

Minor Changes

There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.

The new setting is called minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, setting minimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

If you set minimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under the minimumReleaseAgeExclude setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:
```
minimumReleaseAgeExclude:
  - webpack
```
Related issue: #9921.
Added support for finders #9946.

In the past, pnpm list and pnpm why could only search for dependencies by name (and optionally version). For example:
```
pnpm why minimist
```
prints the chain of dependencies to any installed instance of minimist:
```
verdaccio 5.20.1
├─┬ handlebars 4.7.7
│ └── minimist 1.2.8
└─┬ mv 2.1.1
  └─┬ mkdirp 0.5.6
    └── minimist 1.2.8
```
What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have react@17 in their peer dependencies?

This is now possible with "finder functions". Finder functions can be declared in .pnpmfile.cjs and invoked with the --find-by=<function name> flag when running pnpm list or pnpm why.

Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our .pnpmfile.cjs:
```
module.exports = {
  finders: {
    react17: (ctx) => {
      return ctx.readManifest().peerDependencies?.react === "^17.0.0";
    },
  },
};
```
Now we can use this finder function by running:
```
pnpm why --find-by=react17
```
pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.
```
@&#8203;apollo/client 4.0.4
├── @&#8203;graphql-typed-document-node/core 3.2.0
└── graphql-tag 2.12.6
```
It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:
```
module.exports = {
  finders: {
    react17: (ctx) => {
      const manifest = ctx.readManifest();
      if (manifest.peerDependencies?.react === "^17.0.0") {
        return `license: ${manifest.license}`;
      }
      return false;
    },
  },
};
```
Every matched package will also print out the license from its package.json:
```
@&#8203;apollo/client 4.0.4
├── @&#8203;graphql-typed-document-node/core 3.2.0
│   license: MIT
└── graphql-tag 2.12.6
    license: MIT
```

Patch Changes

Fix deprecation warning printed when executing pnpm with Node.js 24 #9529.
Throw an error if nodeVersion is not set to an exact semver version #9934.
pnpm publish should be able to publish a .tar.gz file #9927.
Canceling a running process with Ctrl-C should make pnpm run return a non-zero exit code #9626.

`v10.15.1`

Compare Source

Patch Changes

Fix .pnp.cjs crash when importing subpath #9904.
When resolving peer dependencies, pnpm looks whether the peer dependency is present in the root workspace project's dependencies. This change makes it so that the peer dependency is correctly resolved even from aliased npm-hosted dependencies or other types of dependencies #9913.

`v10.15.0`

Compare Source

Minor Changes

Added the cleanupUnusedCatalogs configuration. When set to true, pnpm will remove unused catalog entries during installation #9793.
Automatically load pnpmfiles from config dependencies that are named @*/pnpm-plugin-* #9780.
pnpm config get now prints an INI string for an object value #9797.
pnpm config get now accepts property paths (e.g. pnpm config get catalog.react, pnpm config get .catalog.react, pnpm config get 'packageExtensions["@babel/parser"].peerDependencies["@babel/types"]'), and pnpm config set now accepts dot-leading or subscripted keys (e.g. pnpm config set .ignoreScripts true).
pnpm config get --json now prints a JSON serialization of config value, and pnpm config set --json now parses the input value as JSON.

Patch Changes

Semi-breaking. When automatically installing missing peer dependencies, prefer versions that are already present in the direct dependencies of the root workspace package #9835.
When executing the pnpm create command, must verify whether the node version is supported even if a cache already exists #9775.
When making requests for the non-abbreviated packument, add */* to the Accept header to avoid getting a 406 error on AWS CodeArtifact #9862.
The standalone exe version of pnpm works with glibc 2.26 again #9734.
Fix a regression in which pnpm dlx pkg --help doesn't pass --help to pkg #9823.

`v10.14.0`

Compare Source

Minor Changes

Added support for JavaScript runtime resolution

Declare Node.js, Deno, or Bun in devEngines.runtime (inside package.json) and let pnpm download and pin it automatically.

Usage example:
```
{
  "devEngines": {
    "runtime": {
      "name": "node",
      "version": "^24.4.0",
      "onFail": "download" (we only support the "download" value for now)
    }
  }
}
```
How it works:
1. pnpm install resolves your specified range to the latest matching runtime version.
2. The exact version (and checksum) is saved in the lockfile.
3. Scripts use the local runtime, ensuring consistency across environments.
Why this is better:
1. This new setting supports also Deno and Bun (vs. our Node-only settings useNodeVersion and executionEnv.nodeVersion)
2. Supports version ranges (not just a fixed version).
3. The resolved version is stored in the pnpm lockfile, along with an integrity checksum for future validation of the Node.js content's validity.
4. It can be used on any workspace project (like executionEnv.nodeVersion). So, different projects in a workspace can use different runtimes.
5. For now devEngines.runtime setting will install the runtime locally, which we will improve in future versions of pnpm by using a shared location on the computer.
Related PR: #9755.
Add --cpu, --libc, and --os to pnpm install, pnpm add, and pnpm dlx to customize supportedArchitectures via the CLI #7510.

Patch Changes

Fix a bug in which pnpm add downloads packages whose libc differ from pnpm.supportedArchitectures.libc.
The integrities of the downloaded Node.js artifacts are verified #9750.
Allow dlx to parse CLI flags and options between the dlx command and the command to run or between the dlx command and -- #9719.
pnpm install --prod should removing hoisted dev dependencies #9782.
Fix an edge case bug causing local tarballs to not re-link into the virtual store. This bug would happen when changing the contents of the tarball without renaming the file and running a filtered install.
Fix a bug causing pnpm install to incorrectly assume the lockfile is up to date after changing a local tarball that has peers dependencies.

`v10.13.1`

Compare Source

Patch Changes

Run user defined pnpmfiles after pnpmfiles of plugins.

`v10.13.0`

Compare Source

Minor Changes

Added the possibility to load multiple pnpmfiles. The pnpmfile setting can now accept a list of pnpmfile locations #9702.
pnpm will now automatically load the pnpmfile.cjs file from any config dependency named @pnpm/plugin-* or pnpm-plugin-* #9729.

The order in which config dependencies are initialized should not matter — they are initialized in alphabetical order. If a specific order is needed, the paths to the pnpmfile.cjs files in the config dependencies can be explicitly listed using the pnpmfile setting in pnpm-workspace.yaml.

Patch Changes

When patching dependencies installed via pkg.pr.new, treat them as Git tarball URLs #9694.
Prevent conflicts between local projects' config and the global config in dangerouslyAllowAllBuilds, onlyBuiltDependencies, onlyBuiltDependenciesFile, and neverBuiltDependencies #9628.
Sort keys in pnpm-workspace.yaml with deep #9701.
The pnpm rebuild command should not add pkgs included in ignoredBuiltDependencies to ignoredBuilds in node_modules/.modules.yaml #9338.
Replaced shell-quote with shlex for quoting command arguments #9381.

`v10.12.4`

Compare Source

Patch Changes

Fix pnpm licenses command for local dependencies #9583.
Fix a bug in which pnpm ls --filter=not-exist --json prints nothing instead of an empty array #9672.
Fix a deadlock that sometimes happens during peer dependency resolution #9673.
Running pnpm install after pnpm fetch should hoist all dependencies that need to be hoisted.
Fixes a regression introduced in [v10.12.2] by [#9648]; resolves [#9689].

[v10.12.2]: https://github.com/pnpm/pnpm/releases/tag/v10.12.2Add commentMore actions
[#9648]: #9648
[#9689]: #9689

`v10.12.3`

Compare Source

Patch Changes

Restore hoisting of optional peer dependencies when installing with an outdated lockfile.
Regression introduced in v10.12.2 by #9648; resolves #9685.

`v10.12.2`

Compare Source

Patch Changes

Fixed hoisting with enableGlobalVirtualStore set to true #9648.
Fix the --help and -h flags not working as expected for the pnpm create command.
The dependency package path output by the pnpm licenses list --json command is incorrect.
Fix a bug in which pnpm deploy fails due to overridden dependencies having peer dependencies causing ERR_PNPM_OUTDATED_LOCKFILE #9595.

`v10.12.1`

Minor Changes

Experimental. Added support for global virtual stores. When enabled, node_modules contains only symlinks to a central virtual store, rather to node_modules/.pnpm. By default, this central store is located at <store-path>/links (you can find the store path by running pnpm store path).

In the central virtual store, each package is hard linked into a directory whose name is the hash of its dependency graph. This allows multiple projects on the system to symlink shared dependencies from this central location, significantly improving installation speed when a warm cache is available.

This is conceptually similar to how NixOS manages packages, using dependency graph hashes to create isolated and reusable package directories.

To enable the global virtual store, set enableGlobalVirtualStore: true in your root pnpm-workspace.yaml, or globally via:
```
pnpm config -g set enable-global-virtual-store true
```
NOTE: In CI environments, where caches are typically cold, this setting may slow down installation. pnpm automatically disables the global virtual store when running in CI.

Related PR: #8190

The pnpm update command now supports updating catalog: protocol dependencies and writes new specifiers to pnpm-workspace.yaml.
Added two new CLI options (--save-catalog and --save-catalog-name=<name>) to pnpm add to save new dependencies as catalog entries. catalog: or catalog:<name> will be added to package.json and the package specifier will be added to the catalogs or catalog[<name>] object in pnpm-workspace.yaml #9425.
Semi-breaking. The keys used for side-effects caches have changed. If you have a side-effects cache generated by a previous version of pnpm, the new version will not use it and will create a new cache instead #9605.
Added a new setting called ci for explicitly telling pnpm if the current environment is a CI or not.

Patch Changes

Sort versions printed by pnpm patch using semantic versioning rules.
Improve the way the error message displays mismatched specifiers. Show differences instead of 2 whole objects #9598.
Revert #9574 to fix a regression #9596.

`v10.11.1`

Compare Source

Patch Changes

Fix an issue in which pnpm deploy --legacy creates unexpected directories when the root package.json has a workspace package as a peer dependency #9550.
Dependencies specified via a URL that redirects will only be locked to the target if it is immutable, fixing a regression when installing from GitHub releases. (#9531)
Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #9505.
Use pnpm_config_ env variables instead of npm_config_ #9571.
Fix a regression (in v10.9.0) causing the --lockfile-only flag on pnpm update to produce a different pnpm-lock.yaml than an update without the flag.
Let pnpm deploy work in repos with overrides when inject-workspace-packages=true #9283.
Fixed the problem of path loss caused by parsing URL address. Fixes a regression shipped in pnpm v10.11 via #9502.
pnpm -r --silent run should not print out section #9563.

`v10.11.0`

Compare Source

Minor Changes

A new setting added for pnpm init to create a package.json with type=module, when init-type is module. Works as a flag for the init command too #9463.
Added support for Nushell to pnpm setup #6476.
Added two new flags to the pnpm audit command, --ignore and --ignore-unfixable #8474.

Ignore all vulnerabilities that have no solution:
```
> pnpm audit --ignore-unfixable
```
Provide a list of CVE's to ignore those specifically, even if they have a resolution.
```
> pnpm audit --ignore=CVE-2021-1234 --ignore=CVE-2021-5678
```
Added support for recursively running pack in every project of a workspace #4351.

Now you can run pnpm -r pack to pack all packages in the workspace.

Patch Changes

pnpm version management should work, when dangerouslyAllowAllBuilds is set to true #9472.
pnpm link should work from inside a workspace #9506.
Set the default workspaceConcurrency to Math.min(os.availableParallelism(), 4) #9493.
Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #9505.
Read updateConfig from pnpm-workspace.yaml #9500.
Add support for recursive pack
Remove url.parse usage to fix warning on Node.js 24 #9492.
pnpm run should be able to run commands from the workspace root, if ignoreScripts is set tot true #4858.

`v10.10.0`

Compare Source

Minor Changes

Allow loading the preResolution, importPackage, and fetchers hooks from local pnpmfile.

Patch Changes

Fix cd command, when shellEmulator is true #7838.
Sort keys in pnpm-workspace.yaml #9453.
Pass the npm_package_json environment variable to the executed scripts #9452.
Fixed a mistake in the description of the --reporter=silent option.

`v10.9.0`

Compare Source

Minor Changes

Added support for installing JSR packages. You can now install JSR packages using the following syntax:
```
pnpm add jsr:<pkg_name>
```
or with a version range:
```
pnpm add jsr:<pkg_name>@&#8203;<range>
```
For example, running:
```
pnpm add jsr:@&#8203;foo/bar
```
will add the following entry to your package.json:
```
{
  "dependencies": {
    "@&#8203;foo/bar": "jsr:^0.1.2"
  }
}
```
When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:
```
{
  "dependencies": {
    "@&#8203;foo/bar": "npm:@&#8203;jsr/foo__bar@^0.1.2"
  }
}
```
Related issue: #8941.

Note: The @jsr scope defaults to https://npm.jsr.io/ if the @jsr:registry setting is not defined.
Added a new setting, dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this to pnpm-workspace.yaml:
```
neverBuiltDependencies: []
```
dangerouslyAllowAllBuilds has the same effect but also allows to be set globally via:
```
pnpm config set dangerouslyAllowAllBuilds true
```
It can also be set when running a command:
```
pnpm install --dangerously-allow-all-builds
```

Patch Changes

Fix a false negative in verifyDepsBeforeRun when nodeLinker is hoisted and there is a workspace package without dependencies and node_modules directory #9424.
Explicitly drop verifyDepsBeforeRun support for nodeLinker: pnp. Combining verifyDepsBeforeRun and nodeLinker: pnp will now print a warning.

`v10.8.1`

Compare Source

Patch Changes

Removed bright white highlighting, which didn't look good on some light themes #9389.
If there is no pnpm related configuration in package.json, onlyBuiltDependencies will be written to pnpm-workspace.yaml file #9404.

`v10.8.0`

Compare Source

Minor Changes

Experimental. A new hook is supported for updating configuration settings. The hook can be provided via .pnpmfile.cjs. For example:

module.exports = {
  hooks: {
    updateConfig: (config) => ({
      ...config,
      nodeLinker: "hoisted",
    }),
  },
};

Now you can use the pnpm add command with the --config flag to install new configurational dependencies #9377.

Patch Changes

Do not hang indefinitely, when there is a glob that starts with !/ in pnpm-workspace.yaml. This fixes a regression introduced by #9169.
pnpm audit --fix should update the overrides in pnpm-workspace.yaml.
pnpm link should update overrides in pnpm-workspace.yaml, not in package.json #9365.

`v10.7.1`

Compare Source

Patch Changes

pnpm config set should convert the settings to their correct type before adding them to pnpm-workspace.yaml #9355.
pnpm config get should read auth related settings via npm CLI #9345.
Replace leading ~/ in a path in .npmrc with the home directory #9217.

`v10.7.0`

Compare Source

Minor Changes

pnpm config get and list also show settings set in pnpm-workspace.yaml files #9316.
It should be possible to use env variables in pnpm-workspace.yaml setting names and value.
Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

For example:
```
patchedDependencies:
  foo: patches/foo-1.patch
  foo@^2.0.0: patches/foo-2.patch
  [email protected]: patches/foo-3.patch
```
The above configuration would apply patches/foo-3.patch to [email protected], patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.
[!WARNING]
The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:
```
# pnpm-workspace.yaml
patchedDependencies:
  # the specialized sub range
  '[email protected]': patches/foo.2.2.0-2.8.0.patch
  # the more general patch, excluding the sub range above
  'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch
```
In most cases, however, it's sufficient to just define an exact version to override the range.
pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #9316.
Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.
Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes

Remove dependency paths from audit output to prevent out-of-memory errors #9280.

`v10.6.5`

Compare Source

Patch Changes

Remove warnings after having explicitly approved no builds #9296.
When installing different dependency packages, should retain the ignoredBuilds field in the .modules.yaml file #9240.
Fix usages of the catalog: protocol in injected local workspace packages. This previously errored with ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER. #8715
Setting workspace-concurrency to less than or equal to 0 should work #9297.

`v10.6.4`

Compare Source

Patch Changes

Fix pnpm dlx with --allow-build flag #9263.
Invalid Node.js version in use-node-version should not cause pnpm itself to break #9276.
The max amount of workers running for linking packages from the store has been reduced to 4 to achieve optimal results #9286. The workers are performing many file system operations, so increasing the number of CPUs doesn't help performance after some point.

`v10.6.3`

Compare Source

Patch Changes

pnpm install --prod=false should not crash, when executed in a project with a pnpm-workspace.yaml file #9233. This fixes regression introduced via #9211.
Add the missing node-options config to recursive run #9180.
Removed a branching code path that only executed when dedupe-peer-dependents=false. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that override dedupe-peer-dependents to false. There should be less unique bugs from turning off dedupe-peer-dependents.

See details in #9259.

`v10.6.2`

Compare Source

Patch Changes

pnpm self-update should always update the version in the packageManager field of package.json.
Fix running pnpm CLI from pnpm CLI on Windows when the CLI is bundled to an executable #8971.
pnpm patch-commit will now use the same filesystem as the store directory to compare and create patch files.
Don't show info output when --loglevel=error is used.
peerDependencyRules should be set in pnpm-workspace.yaml to take effect.

`v10.6.1`

Compare Source

Patch Changes

The pnpm CLI process should not stay hanging, when --silent reporting is used.
When --loglevel is set to error, don't show installation summary, execution time, and big tarball download progress.
Don't ignore pnpm.patchedDependencies from package.json #9226.
When executing the approve-builds command, if package.json contains onlyBuiltDependencies or ignoredBuiltDependencies, the selected dependency package will continue to be written into package.json.
When a package version cannot be found in the package metadata, print the registry from which the package was fetched.

`v10.6.0`

Compare Source

Minor Changes

pnpm-workspace.yaml can now hold all the settings that .npmrc accepts. The settings should use camelCase #9211.

pnpm-workspace.yaml example:
```
verifyDepsBeforeRun: install
optimisticRepeatInstall: true
publicHoistPattern:
  - "*types*"
  - "!@&#8203;types/react"
```
Projects using a file: dependency on a local tarball file (i.e. .tgz, .tar.gz, .tar) will see a performance improvement during installation. Previously, using a file: dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.

Patch Changes

pnpm self-update should not leave a directory with a broken pnpm installation if the installation fails.
fast-glob replace with tinyglobby to reduce the size of the pnpm CLI dependencies #9169.
pnpm deploy should not remove fields from the deployed package's package.json file #9215.
pnpm self-update should not read the pnpm settings from the package.json file in the current working directory.
Fix pnpm deploy creating a package.json without the imports and license field #9193.
pnpm update -i should list only packages that have newer versions #9206.
Fix a bug causing entries in the catalogs section of the pnpm-lock.yaml file to be removed when dedupe-peer-dependents=false on a filtered install. #9112

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot force-pushed the renovate/pnpm-10.x branch from 946c9e2 to 5c7ba4f Compare March 7, 2025 06:38

renovate bot changed the title ~~chore(deps): update pnpm to v10.6.0~~ chore(deps): update pnpm to v10.6.1 Mar 7, 2025

renovate bot changed the title ~~chore(deps): update pnpm to v10.6.1~~ chore(deps): update pnpm to v10.6.2 Mar 10, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch 2 times, most recently from cf0bd43 to 1c5fe23 Compare March 13, 2025 18:40

renovate bot changed the title ~~chore(deps): update pnpm to v10.6.2~~ chore(deps): update pnpm to v10.6.3 Mar 13, 2025

renovate bot changed the title ~~chore(deps): update pnpm to v10.6.3~~ chore(deps): update pnpm to v10.6.4 Mar 17, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from 1c5fe23 to bcf4f52 Compare March 17, 2025 20:48

renovate bot changed the title ~~chore(deps): update pnpm to v10.6.4~~ chore(deps): update pnpm to v10.6.5 Mar 19, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch 2 times, most recently from 7e05938 to ec5a998 Compare March 26, 2025 15:23

renovate bot changed the title ~~chore(deps): update pnpm to v10.6.5~~ chore(deps): update pnpm to v10.7.0 Mar 26, 2025

renovate bot changed the title ~~chore(deps): update pnpm to v10.7.0~~ chore(deps): update pnpm to v10.7.1 Apr 1, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch 2 times, most recently from 1a442de to f20382f Compare April 7, 2025 18:36

renovate bot changed the title ~~chore(deps): update pnpm to v10.7.1~~ chore(deps): update pnpm to v10.8.0 Apr 7, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from f20382f to b47f5f2 Compare April 14, 2025 17:03

renovate bot changed the title ~~chore(deps): update pnpm to v10.8.0~~ chore(deps): update pnpm to v10.8.1 Apr 14, 2025

renovate bot changed the title ~~chore(deps): update pnpm to v10.8.1~~ chore(deps): update pnpm to v10.9.0 Apr 21, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch 2 times, most recently from 2988ec3 to 42b10f7 Compare April 28, 2025 01:52

renovate bot changed the title ~~chore(deps): update pnpm to v10.9.0~~ chore(deps): update pnpm to v10.10.0 Apr 28, 2025

renovate bot changed the title ~~chore(deps): update pnpm to v10.10.0~~ chore(deps): update pnpm to v10.11.0 May 13, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from 42b10f7 to ac0d730 Compare May 13, 2025 17:00

renovate bot force-pushed the renovate/pnpm-10.x branch from ac0d730 to d5302f0 Compare June 2, 2025 14:41

renovate bot changed the title ~~chore(deps): update pnpm to v10.11.0~~ chore(deps): update pnpm to v10.11.1 Jun 2, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from d5302f0 to bf0513b Compare June 8, 2025 17:41

renovate bot changed the title ~~chore(deps): update pnpm to v10.11.1~~ chore(deps): update pnpm to v10.12.1 Jun 8, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from bf0513b to 3de4373 Compare June 23, 2025 02:45

renovate bot changed the title ~~chore(deps): update pnpm to v10.12.1~~ chore(deps): update pnpm to v10.12.2 Jun 23, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from 3de4373 to fc6963c Compare June 24, 2025 13:14

renovate bot changed the title ~~chore(deps): update pnpm to v10.12.2~~ chore(deps): update pnpm to v10.12.3 Jun 24, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from fc6963c to a150d0a Compare June 26, 2025 19:41

renovate bot changed the title ~~chore(deps): update pnpm to v10.12.3~~ chore(deps): update pnpm to v10.12.4 Jun 26, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from a150d0a to f167922 Compare July 9, 2025 14:36

renovate bot changed the title ~~chore(deps): update pnpm to v10.12.4~~ chore(deps): update pnpm to v10.13.1 Jul 9, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from f167922 to ea1c829 Compare August 7, 2025 11:24

renovate bot changed the title ~~chore(deps): update pnpm to v10.13.1~~ chore(deps): update pnpm to v10.14.0 Aug 7, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from ea1c829 to 8e10c35 Compare August 19, 2025 19:05

renovate bot changed the title ~~chore(deps): update pnpm to v10.14.0~~ chore(deps): update pnpm to v10.15.0 Aug 19, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from 8e10c35 to 49be11a Compare September 1, 2025 23:04

renovate bot changed the title ~~chore(deps): update pnpm to v10.15.0~~ chore(deps): update pnpm to v10.15.1 Sep 1, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from 49be11a to f689439 Compare September 13, 2025 19:04

renovate bot changed the title ~~chore(deps): update pnpm to v10.15.1~~ chore(deps): update pnpm to v10.16.1 Sep 13, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from f689439 to 71c25c0 Compare September 17, 2025 16:22

renovate bot changed the title ~~chore(deps): update pnpm to v10.16.1~~ chore(deps): update pnpm to v10.17.0 Sep 17, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from 71c25c0 to c257662 Compare September 22, 2025 14:54

renovate bot changed the title ~~chore(deps): update pnpm to v10.17.0~~ chore(deps): update pnpm to v10.17.1 Sep 22, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from c257662 to 256d93c Compare October 2, 2025 17:05

renovate bot changed the title ~~chore(deps): update pnpm to v10.17.1~~ chore(deps): update pnpm to v10.18.0 Oct 2, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from 256d93c to 2fa4345 Compare October 6, 2025 15:07

renovate bot changed the title ~~chore(deps): update pnpm to v10.18.0~~ chore(deps): update pnpm to v10.18.1 Oct 6, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from 2fa4345 to d47b57d Compare October 10, 2025 01:53

renovate bot changed the title ~~chore(deps): update pnpm to v10.18.1~~ chore(deps): update pnpm to v10.18.2 Oct 10, 2025

renovate bot force-pushed the renovate/pnpm-10.x branch from d47b57d to a9d687a Compare October 14, 2025 10:02

renovate bot changed the title ~~chore(deps): update pnpm to v10.18.2~~ chore(deps): update pnpm to v10.18.3 Oct 14, 2025

chore(deps): update pnpm to v10.19.0

47ce834

renovate bot force-pushed the renovate/pnpm-10.x branch from a9d687a to 47ce834 Compare October 21, 2025 22:12

renovate bot changed the title ~~chore(deps): update pnpm to v10.18.3~~ chore(deps): update pnpm to v10.19.0 Oct 21, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update pnpm to v10.19.0 #90

chore(deps): update pnpm to v10.19.0 #90

Uh oh!

renovate bot commented Mar 6, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

chore(deps): update pnpm to v10.19.0 #90

Are you sure you want to change the base?

chore(deps): update pnpm to v10.19.0 #90

Uh oh!

Conversation

renovate bot commented Mar 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Mar 6, 2025 •

edited

Loading